cdc Performance Reporting Facility 1.0 ERS Feb84 free download

File name Performance_Reporting_Facility_1.0_ERS_Feb84.pdf

PERFORMANCE REPORTING FACILITY Version 1.0 EXTERNAL REFERENCE SPECIFICATION Canadian Development Division Perform.nee Evaluation Unit October l5, 1982 Revised December 9, 1983 Revised February 24,1984 Control Data Private 1-1 Performance Reporting Facility ERS 24 febB4 1.0 PRF DVE: RVI EW 'ThePerfa rmanee Rapor ting fae II i tv (PRf) is an Integrated pertorm~nce reporting package tor NDS/VE. Some portions of PRF run on NOS/VE in 180 stlta Mhile the rest of the package currently runs in 17Q state under H05/170. PRF is intended to be a modular system which can be extended Into a full short and long term perform~nc. tracking system. The current PRF is based on the PMF hardware option for CY8ER 190. In the longer term, It wltl accept performance data from other sources and maintain 3 performance dateb9se. Control Data Private 1-2 Performance Reporting Fecllity ERS 24 Feb 84 1.0 PRf aVE RV I EW 1.1 PMF HARDWAR.E The Performance Monitoring Facility (PMF) Is a CyaeR 180 hardware GPtion which provides a set or hardware counters and event buffers designed to collect performance data about the system. Significant hardware states and/or events may be timed and counted throuah PMF counters. Data on software events within NOS/\/Eandlts product set ma,Y be obtained by insertingkeypoint Instructions in the software which may be collected through the PHf keyooint buffers. Because PM~ uses a combination of hardware and software monitoring techniques, i t is s good example of an integrated hybrid performance monitor. 1.1.1 PMF COUNTERS PMF hardware contains eight 32-bit counters which may count hardware events and time system st3tes. The list of events and states supported is model dependent and there is a se1ection code associated with each one. A limited amount of signa' combination Is allowed through AlB counter pairings and appropriate control qod~s. Event/state selection and signa' combination are control.ed through settings in register 22. To be supplied. 1.1.2 K~ypaINT INSTRUCTIONS Keypoints are special 180 instructions which place an indication of significant software events Into the FIFO burfer In PMf hardware or cause a keypoint trap to allow the data to be cot'ected by softNare. These Instructions act as NO-OPs to the NOS/VE software unless keypoint traps are enabled. In any system with the PM~ hardware option, hardware collection rather than software collection should be used as there is almost n